-
Notifications
You must be signed in to change notification settings - Fork 30.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
meta: move one or more collaborators to emeritus #56580
Conversation
Anatoli is still a TSC regular member, hence the linter error. |
/cc @apapirovski FYI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@targos I think when a collaborator drops out due to inactivity they move from regular to emeritus for the TSC, right? If so I'm happy to open a PR which will do that move. |
Just going to see if I can give Anatoli a heads up through email and then will open the PR to move him to emeritus, that should resolve the linter issue. |
PR to move Anatoli to emeritus - #56592 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Thanks!
cd71cc9
to
7ce3b50
Compare
I don't see a way to rebase this so that the linter passes (which it should since #56592 landed). Unless somebody has a better suggestion by tomorrow I'll close this PR and re-run the action to get a new PR we can land. |
Landed in 532fff6 |
PR-URL: #56580 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Ulises Gascón <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Rafael Gonzaga <[email protected]>
This PR was generated by the
find-inactive-collaborators.yml
workflow.@nodejs/tsc Please follow up with the offboarding tasks.